Pharmacy order processing system

ABSTRACT

A pharmacy order processing system includes a container disassembly workstation defining a container disassembly workspace and a bulk container area including a plurality of bulk containers configured to receive a plurality of pharmaceuticals. The container disassembly workstation includes a holding area, a cutter device, a container manipulation device, a pharmaceutical receptacle, and a container receptacle. The cutter device includes a cutter head and is configured to cut through at least one wall of at least one container to separate at least a first portion of the at least one container of the plurality of containers from a second portion of the at least one container when the at least one container is in a cutter position. The container manipulation includes a gripper device and is configured to move the at least one container between at least the holding position and the cutter position within the container disassembly workspace.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/996,909, filed on Jun. 4, 2018; the entire disclosure of which isincorporated herein by reference.

FIELD

The present disclosure relates generally to the technical field ofpharmacy order processing, and more particularly, to methods and systemsfor removing pharmaceuticals from relatively small volume pharmaceuticalcontainers and transferring the removed pharmaceuticals to relativelylarger volume pharmaceutical containers, especially in a high volume,specialty, or partially-automated order processing center.

BACKGROUND

This Background section is intended to introduce the reader to variousaspects of art that may be related to various aspects of the presentdisclosure, which are described and/or claimed below. This discussion isbelieved to be helpful in providing the reader with backgroundinformation to facilitate a better understanding of the various aspectsof the present disclosure. Accordingly, it should be understood thatthese statements are to be read in this light, and not as admissions ofprior art.

Pharmaceutical order processing systems typically involve laborintensive processes to remove pharmaceuticals from manufacturerpackaging, transfer the pharmaceuticals to a bulk storage container,retrieve the pharmaceuticals, and fill and package the many pharmacyorders. Many of the pharmacy orders are custom or specialty orders thatrequire a quantity of specific pharmaceuticals that necessitatesemptying multiple original manufacturer containers to fill a singleorder, and thus the process for filling the orders is difficult toefficiently complete and requires substantial operator interactionthroughout the process. Improved systems and methods for filling customor specialty pharmacy orders at a high volume to improve orderfulfillment realization and customer satisfaction are needed.

BRIEF SUMMARY

In one aspect, a pharmacy order processing system includes a containerdisassembly workstation defining a container disassembly workspace and abulk container area including a plurality of bulk containers. Thecontainer disassembly workstation includes a holding area, a cutterdevice, a container manipulation device, a pharmaceutical receptacle,and a container receptacle. The holding area is sized to retain aplurality of containers in a holding position, wherein a plurality ofpharmaceuticals are contained within each container of the plurality ofcontainers. The cutter device includes a cutter head and is configuredto cut through at least one wall of at least one container to separateat least a first portion of the at least one container of the pluralityof containers from a second portion of the at least one container whenthe at least one container is in a cutter position. The containermanipulation includes a gripper device and is configured to move the atleast one container between at least the holding position and the cutterposition within the container disassembly workspace. The pharmaceuticalreceptacle is sized to receive the plurality of pharmaceuticals, whereinthe plurality of pharmaceuticals are received from the at least onecontainer after the first portion of the at least one container isseparated from the second portion of the at least one container. Thecontainer receptacle defines an opening sized to receive the firstportion of the at least one container and the second portion of the atleast one container. The bulk containers are configured to receive aplurality of the plurality of pharmaceuticals from the containerreceptacle.

In another aspect, a container disassembly workstation defining acontainer disassembly workspace includes a holding area, a cutterdevice, a container manipulation device, a pharmaceutical receptacle,and a container receptacle. The holding area is configured to retain aplurality of containers in a holding position, wherein a plurality ofpharmaceuticals are contained within each container of the plurality ofcontainers. The cutter device is configured to separate at least a firstportion of at least one container of the plurality of containers from asecond portion of the at least one container in a cutting position ofthe cutter device. A container manipulation device is configured to movethe at least one container within the container disassembly workspacesuch that the at least one container is moved between the holdingposition and the cutting position. The pharmaceutical receptacle isconfigured to receive the plurality of pharmaceuticals, wherein theplurality of pharmaceuticals are received from the at least onecontainer after the first portion of the at least one container isseparated from the second portion of the at least one container. Thecontainer receptacle is configured to receive the first portion of theat least one container and the second portion of the at least onecontainer.

In yet another aspect, a method of disassembling a container includesscanning a holding area to determine if at least one containercontaining a plurality of pharmaceutical products is positioned in aholding position of the holding area of a container disassemblyworkstation. The method also includes capturing the at least onecontainer with a container manipulation device. The method furtherincludes moving the at least one container from the holding position toa cutter position proximate a cutter device. The method includesseparating a first portion of the at least one container from a secondportion of the at least one container using the cutter device. Themethod also includes transferring the plurality of pharmaceuticalproducts from at least one of the first portion of the at least onecontainer and the second portion of the at least one container to apharmaceutical receptacle, wherein the pharmaceutical receptacle issized to receive the plurality of pharmaceuticals. Finally, the methodincludes placing at least one of the first portion of the at least onecontainer and the second portion of the at least one container in acontainer receptacle wherein the container receptacle defines an openingsized to receive the first portion of the at least one container and thesecond portion of the at least one container.

Various refinements exist of the features noted in relation to theabove-mentioned aspects. Further features may also be incorporated inthe above-mentioned aspects as well. These refinements and additionalfeatures may exist individually or in any combination. For instance,various features discussed below in relation to any of the illustratedembodiments may be incorporated into any of the above-described aspects,alone or in any combination.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example implementation of a pharmacyorder processing system, according to an example embodiment;

FIG. 2 is a plan view of a layout of the pharmacy order processingsystem shown in FIG. 1 according to an example embodiment;

FIG. 3 is a front view of a container disassembly workstation for usewith the system shown in FIG. 1 according to an example embodiment;

FIG. 4 is a front view of a container that may be used with thecontainer disassembly workstation shown in FIG. 3 according to anexample embodiment;

FIG. 5 is a perspective view of a cutter device for use with thecontainer disassembly workstation shown in FIG. 3 illustrated in anon-cutting position according to an example embodiment;

FIG. 6 is a plan view of the cutter device shown in FIG. 5 according toan example embodiment;

FIG. 7 is a perspective of the cutter device shown in FIG. 5 illustratedin a cutting position and illustrating a container manipulation deviceaccording to an example embodiment;

FIG. 8 is a front view of the cutter device shown in FIG. 7 according toan example embodiment; and

FIGS. 9A and 9B are an example process flow illustrating a method forprocessing pharmacy orders, according to an example embodiment.

In the drawings, reference numbers may be reused to identify similarand/or identical elements.

Corresponding reference characters indicate corresponding partsthroughout the several views of the drawings.

DETAILED DESCRIPTION

Example systems and methods for processing a pharmacy order, forexample, in a pharmacy, are described. In the following description, forpurposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of example embodiments. Itwill be evident, however, to one of ordinary skill in the art that theseembodiments may be practiced without these specific details.

Generally, a prescription order is generated for a pharmacy, and in someembodiments a high volume pharmacy. The prescription order may includemore than one pharmaceutical, or prescription drug, for fulfillment.Each pharmaceutical in a prescription order is an order component of theprescription order. Generally, the order components are pill bottles,liquid bottles, blister packs, unit-of-use packs, injectable package,spray bottles, tubes, ampoules, drop counters, insulated boxes,child-resistant containers, or other packaging having a quantity of apharmaceutical contained therein, the pharmaceuticals being required forthe orders in varying and sometimes numerous quantities.

FIG. 1 is a block diagram of an example implementation of a prescriptionorder processing system 100 for a specialty pharmacy, according to anexample embodiment. While the prescription order processing system 100is generally described as being deployed in a specialty or a fulfillmentcenter (e.g., a mail order pharmacy, a direct delivery pharmacy, etc.,and the like), the prescription order processing system 100 and/orcomponents thereof may otherwise be deployed (e.g., in a high volumepharmacy, etc.). A specialty pharmacy may be a pharmacy that is capableof filling prescriptions automatically, mechanically, manually, or acombination thereof. The prescription order processing system 100 mayinclude a benefit manager device 106 and an order processing device 102in communication with each other directly and/or over a network 104. Thesystem may also include a storage device 108.

The benefit manager device 106 is a device operated by an entity that isat least partially responsible for creation and/or management of thepharmacy or drug benefit. While such entity operating the benefitmanager device 106 is typically a pharmacy benefit manager (PBM), otherentities may operate the benefit manager device 106 on behalf ofthemselves (i.e., the PBMs) or other entities. For example, the benefitmanager device 106 may be operated by a health plan, a retail pharmacychain, a drug wholesaler, a data analytics, or other type ofsoftware-related company, etc., or the like. In some embodiments, a PBMthat provides the pharmacy benefit may also provide one or more than oneadditional benefits including a medical or health benefit, a dentalbenefit, a vision benefit, a wellness benefit, a radiology benefit, apet care benefit, an insurance benefit, a long term care benefit, anursing home benefit, etc., and the like. The PBM may, in addition toits PBM operations, operate one or more than one pharmacies. Thepharmacies may be retail pharmacies, mail order pharmacies, etc.

Some of the operations of the PBM that operates the benefit managerdevice 106 may include the following activities and processes. A member(or a person on behalf of the member) of a pharmacy benefit plan mayobtain a prescription drug at a retail pharmacy location (e.g., alocation of a physical store, etc.) from a pharmacist or a pharmacisttechnician. The member may also obtain the prescription drug throughmail order drug delivery from a mail order pharmacy location, which maybe the prescription order processing system 100. In some embodiments,the member may obtain the prescription drug directly or indirectlythrough the use of a machine, such as a kiosk, vending unit, mobileelectronic device, or a different type of mechanical, electrical,electronic communication device and/or computing device. Such a machinemay be filled with the prescription drug in prescription packaging,which may include multiple prescription components, by the prescriptionorder processing system 100. The pharmacy benefit plan is administeredby or through the benefit manager device 106.

The member may have a copayment for the prescription drug that reflectsan amount of money that the member is responsible to pay the pharmacyfor the prescription drug. The money paid by the member to the pharmacymay come from personal funds of the member, a health savings account(HSA) of the member or the member's family, a health reimbursementarrangement (HRA) of the member or the member's family, a flexiblespending account (FSA) of the member or the member's family, etc., orthe like. In some instances, an employer of the member may directly orindirectly fund or reimburse the member for the copayments.

The amount of the copayment required by the member may vary withdifferent pharmacy benefit plans having different plan sponsors orclients and/or for different prescription drugs. The member's copaymentmay be a flat copayment (e.g., $10, etc.), co-insurance (e.g., 10%,etc.), and/or a deductible (e.g., for first $500 of annual prescriptiondrug expense, etc.) for certain prescription drugs, certain types and/orclasses of prescription drugs, and/or all prescription drugs. Thecopayment may be stored in the storage device 108 or determined by thebenefit manager device 106.

In some instances, the member may not pay the copayment or may only paya portion of the copayment for the prescription drug. For example, if ausual and customary cost for a generic version of a prescription drug is$4, and the member's flat copayment is $20 for the prescription drug,the member may only need to pay $4 to receive the prescription drug. Inanother example involving a worker's compensation claim, no copaymentmay be due by the member for the prescription drug.

In addition, copayments may also vary based on different deliverychannels used for the prescription drug to be received. For example, thecopayment for receiving the prescription drug from a mail order pharmacylocation may be less than the copayment for receiving the prescriptiondrug from a retail pharmacy location.

In conjunction with receiving a copayment (if any) from the member anddispensing the prescription drug to the member, the pharmacy submits aclaim to the PBM for the prescription drug. After receiving the claim,the PBM, e.g., the benefit manager device, may perform certainadjudication operations including verifying eligibility for the member,identifying/reviewing an applicable formulary for the member todetermine any appropriate copayment, coinsurance, and deductible for theprescription drug, and performing a drug utilization review (DUR) on themember. Further, the PBM may provide a response to the pharmacy, e.g.,the pharmacy prescription order processing system 100, followingperformance of at least some of the aforementioned operations.

As part of the adjudication, a plan sponsor (or the PBM on behalf of theplan sponsor) ultimately reimburses the pharmacy for filling theprescription drug when the prescription drug was successfullyadjudicated.

The aforementioned adjudication operations generally occur before thecopayment is received and the prescription drug is dispensed. However insome instances, these operations may occur simultaneously, substantiallysimultaneously, or in a different order. In addition, more or lessadjudication operations may be performed as at least part of theadjudication process.

The amount of reimbursement paid to the pharmacy by a plan sponsorand/or money paid by the member may be determined at least partiallybased on types of pharmacy network in which the pharmacy is included. Insome embodiments, the amount may also be determined based on otherfactors. For example, if the member pays the pharmacy for theprescription drug without using the prescription or drug benefitprovided by the PBM, the amount of money paid by the member may behigher than when the member uses the prescription or drug benefit. Insome embodiments, the amount of money received by the pharmacy fordispensing the prescription drug and for the prescription drug itselfmay be higher than when the member uses the prescription or drugbenefit. Some or all of the foregoing operations may be performed byexecuting instructions stored in the benefit manager device 106 and/oran additional device.

Examples of the network 104 include Mobile Communications (GSM) network,a code division multiple access (CDMA) network, 3rd GenerationPartnership Project (3GPP), an Internet Protocol (IP) network, aWireless Application Protocol (WAP) network, a WiFi network, or an IEEE802.11 standards network, as well as various combinations thereof. Thenetwork 104 may include optical network. The network 104 may be a localarea network or a global communication network, such as the Internet. Insome embodiments, the network 104 may include a network dedicated toprescription orders, e.g., a prescribing network such as the electronicprescribing network operated by Surescripts of Arlington, Va.

Moreover, although the system shows a single network 104, multiplenetworks can be used. The multiple networks may communicate in serieswith each other to link the devices 102-110 or in parallel to link thedevices 102-110.

The order processing device 102 may be a device associated with a retailpharmacy location (e.g., an exclusive pharmacy location, a grocery storewith a retail pharmacy, or a general sales store with a retail pharmacy)or other type of pharmacy location at which a member attempts to obtaina prescription. The order processing device 102 may be utilized by thepharmacy to submit the claim to the PBM for adjudication.

Additionally, in some embodiments, the order processing device 102 mayenable information exchange between the pharmacy and the PBM, forexample, to allow the sharing of member information such as drughistory, and the like, that may allow the pharmacy to better service amember (e.g., by providing more informed therapy consultation and druginteraction information, etc.). In some embodiments, the benefit managerdevice 106 may track prescription drug fulfillment and/or otherinformation for patients that are not members or have not identifiedthemselves as members, at the time (or in conjunction with the time) inwhich they seek to have a prescription filled at a pharmacy.

The order processing device 102 may receive information regardingfilling prescriptions and may direct an order component to one or moredevices of the prescription order processing system 100 at a pharmacy.The order processing device 102 may fulfill, dispense, aggregate, and/orpack the order components of the prescription drugs in accordance withone or more prescription orders directed by the prescription orderprocessing system 100. The order processing device 102 may be deployedin the prescription order processing system 100, or may otherwise beused.

In general, the order processing device 102 is a device located withinor otherwise associated with the pharmacy to enable fulfillment of aprescription and dispensing prescription drugs. In some embodiments, theorder processing device 102 may be an external device separate from thepharmacy and may communicate with other devices located within thepharmacy.

For example, the external order processing device 102 may communicatewith an internal order processing device 102 and/or other deviceslocated within the prescription order processing system 100. In someembodiments, the external order processing device 102 may have limitedfunctionality (e.g., as operated by a patient requesting fulfillment ofa prescription drug), while the internal order processing device 102 mayhave greater functionality (e.g., as operated by a pharmacist).

The order processing device 102 may track the prescription order as itis fulfilled by the prescription order processing system 100. Theprescription order may include one or more than one prescription drugsto be filled by the pharmacy. The order processing device 102 may makepharmacy routing decisions and/or order consolidation decisions for theparticular prescription order. The pharmacy routing decisions includewhat device(s) in the pharmacy are responsible for filling or otherwisehandling certain portions of the prescription order. The orderconsolidation decisions include whether portions of one prescriptionorder or multiple prescription orders should be shipped together for apatient or a patient family. The order processing device 102 may alsotrack and/or schedule literature or paperwork associated with eachprescription order or multiple prescription orders that are beingshipped together.

The order processing device 102 may include circuitry, a processor, amemory to store data and instructions, and communication functionality.The order processing device 102 is dedicated to performing processes,methods and/or instructions described herein. Other types of electronicdevices specifically configured to implement with the processes, methodsand/or instructions described herein may also be used.

In some embodiments, at least some functionalities of the orderprocessing device 102 may be included in the benefit manager device 106.The order processing device 102 may be in a client-server relationshipwith the benefit manager device 106, in a peer-to-peer relationship withthe benefit manager device 106, or in a different type of relationshipwith the benefit manager device 106. The order processing device 102and/or the benefit manager device 106 may communicate directly (e.g., byutilizing a local storage, etc.) and/or through the network 104 (e.g.,by utilizing a cloud configuration or software as a service. etc.) withthe storage device 108.

The storage device 108 may include: a non-transitory storage (e.g.,memory, hard disk, CD-ROM, etc.) in communication with the benefitmanager device 106, and/or the order processing device 102 directlyand/or over the network 104. The non-transitory storage may store orderdata 110, member data 112, claims data 114, drug data 116, prescriptiondata 118, and/or plan sponsor data 120. Further, the prescription orderprocessing system 100 includes additional devices, including at leastone container disassembly workstation 125, tray delivery conveyors 124,picking workstations 126, inspection workstations 130, packing deliveryconveyors 132, packing workstations 134, and shipping conveyors 136,each additional device able to communicate with each other directly orover the network 104.

The order data 110 may be related to a prescription order. The orderdata may include type of the prescription drug (e.g., drug name andstrength, etc.) and quantity of the prescription drug, etc. The orderdata 110 may also include data used for completion of the prescription,such as prescription materials. In general, prescription materialsinclude an electronic copy of information regarding the prescriptiondrug for inclusion with or otherwise in conjunction with the fulfilledprescription. The prescription materials may include electronicinformation regarding drug interaction warnings, recommended usage,possible side effects, expiration date, date of prescribing, or thelike. The order data 110 may be used by a high volume fulfillment centerto fulfill a pharmacy order.

In some embodiments, the order data 110 includes verificationinformation associated with fulfillment of the prescription in thepharmacy. For example, the order data 110 may include videos and/orimages taken of (i) the prescription drug prior to dispensing, duringdispensing, and/or after dispensing, (ii) the prescription container(e.g., a prescription bottle and sealing lid, prescription packaging andthe like) used to contain the prescription drug prior to dispensing,during dispensing, and/or after dispensing, (iii) the packaging and/orpackaging materials used to ship or otherwise deliver the prescriptiondrug prior to dispensing, during dispensing, and/or after dispensing,and/or (iv) the fulfillment process within the pharmacy. Other type ofverification information such as bar code data read from pallets, bins,trays, carts, and the like used to transport prescriptions within thepharmacy may also be stored as order data 110.

The member data 112 includes information regarding the membersassociated with the PBM. The information stored as member data 112 mayinclude personal information, personal health information, protectedhealth information, and the like. Examples of the member data 112include name, address, telephone number, e-mail address, prescriptiondrug history, etc., and the like. The member data 112 may include a plansponsor identifier that identifies the plan sponsor associated with themember and/or a member identifier that identifies the member to the plansponsor. The member data 112 may include a member identifier thatidentifies the plan sponsor associated with the patient and/or a patientidentifier that identifies the patient to the plan sponsor. The memberdata 112 may also include, by way of example, dispensation preferencessuch as type of label, type of cap, message preferences, languagepreferences, or the like.

The member data 112 may be accessed by various devices in the pharmacy,(e.g., the high volume fulfillment center, etc.), to obtain informationutilized for fulfillment and shipping of prescription orders. In someembodiments, an external order processing device 102 operated by or onbehalf of a member may have access to at least a portion of the memberdata 112 for review, verification, etc., or other purposes.

In some embodiments, the member data 112 may include information forpersons who are patients of the pharmacy but are not members in thepharmacy benefit plan being provided by the PBM. For example, thesepatients may obtain drug directly from the pharmacy, through a privatelabel service offered by the pharmacy, the high volume fulfillmentcenter, or otherwise. In general, the use of the terms member andpatient may be used interchangeably herein.

The claims data 114 includes information regarding pharmacy claimsadjudicated by the PBM under a drug benefit program provided by the PBMfor one, or more than one, plan sponsors. In general, the claims data114 includes an identification of the client that sponsors the drugbenefit program under which the claim is made, and/or the member thatpurchased the prescription drug giving rise to the claim, theprescription drug that was filled by the pharmacy (e.g., the nationaldrug code number, etc.), the dispensing date, generic indicator, GPInumber, medication class, the cost of the prescription drug providedunder the drug benefit program, the copay/coinsurance amount, rebateinformation, and/or member eligibility, etc. Additional information maybe included.

In some embodiments, other types of claims beyond prescription drugclaims may be stored in the claims data 114. For example, medicalclaims, dental claims, wellness claims, or other type of healthcare-related claims for members may be stored as a portion of the claimsdata 114.

In some embodiments, the claims data 114 includes claims that identifythe members with whom the claims are associated. In some embodiments,the claims data 114 includes claims that have been de-identified (e.g.,associated with a unique identifier but not with a particular,identifiable member, etc.).

The drug data 116 may include drug name (e.g., technical name and/orcommon name, etc.), other names by which the drug is known by, activeingredients, an image of the drug (e.g., in pill form, etc.), and thelike. The drug data 116 may include information associated with a singlemedication or multiple medications.

The prescription data 118 may include information regardingprescriptions that may be issued by prescribers on behalf of patients,who may be members of the pharmacy benefit plan, for example to befilled by a pharmacy. Examples of the prescription data 118 includepatient names, medication or treatment (such as lab tests), dosinginformation, and the like. The prescriptions may be electronicprescriptions, paper prescriptions that have been scanned, or otherwise.In some embodiments, the dosing information reflects a frequency of use(e.g., once a day, twice a day, before each meal, etc.) and a durationof use (e.g., a few days, a week, a few weeks, a month, etc.).

In some embodiments, the order data 110 may be linked to associatedmember data 112, claims data 114, drug data 116, and/or prescriptiondata 118.

The plan sponsor data 120 includes information regarding the plansponsors of the PBM. Examples of the plan sponsor data 120 includecompany name, company address, contact name, contact telephone number,contact e-mail address, etc., and the like.

FIG. 2 is a plan view of a layout of the prescription order processingsystem 100. The prescription order processing system 100 is configuredto rapidly process, using a plurality of operators 107 at a number ofstations, pharmacy orders from receipt of an order to shipping a packedfilled order.

In the example embodiment, prescription order processing system 100includes an ambient conditions section 146, a refrigerated conditionssection 148, an ATX section 147, and a shipping section 150. Each of theambient conditions section 146 and the refrigerated conditions section148 includes a plurality of picking workstations 126, a plurality ofpacking workstations 134, and at least one inspection workstation 130,each workstation assigned one operator 107. Additionally, therefrigerated conditions section 148 includes at least one containerdisassembly workstation 125 with one assigned operator 107. The ATXsection 147 includes two packing workstations 134 and a pair of qualityassurance workstations 135. In some embodiments, prescription orderprocessing system 100 may include as many types and number ofworkstations and operators 107 as facilitates operation of theprescription order processing system 100. As will be understood by oneof ordinary skill, the ambient conditions section 146 is maintained atsubstantially room temperature, and the refrigerated conditions section148 includes portions that are maintained at a temperature that is lessthan the ambient temperature. In the example embodiment, refrigeratedconditions section 148 includes a plurality of reach-in coolers thatmaintain internal temperatures of between approximately 36° F. and 46°F., and at least one walk-in freezer that maintains an internaltemperature of between approximately −14° F. and 14° F. In the exampleembodiment, each cooler and freezer includes a temperature alarm thatsounds if a given temperature range is not met within a respectivecooler or freezer for a 15 minute period.

In this embodiment, prescription order processing system 100 includes aplurality of ambient conveyors 137 and a plurality of conveyorassemblies 138. The ambient section 146 includes two ambient conveyors137. One ambient conveyor 137 extends between the ambient pickingworkstations 126 and is positioned adjacent to the ambient inspectionworkstation 130. The second ambient conveyor 137 extends between theambient packing workstations 134 and is positioned adjacent to theambient inspection workstation 130 opposite to the first ambientconveyor 137. The refrigerated section 148 includes two conveyorassemblies 138 and a shipping conveyor 136. The first of the conveyorassemblies 138 extends from a first group of refrigerated pickingworkstations 126 through a first group refrigerated packing workstations134 to an intersection with the shipping conveyor 136. The second of theconveyor assemblies 138 extends from a second group of refrigeratedpicking workstations 126, past a refrigerated inspection workstation130, and through a second group of refrigerated packing workstations 134to an intersection with the shipping conveyor 136. The shipping conveyor136 extends from intersections with each of the conveyor assemblies 138to the shipping section 150.

FIG. 3 is a front view of a container disassembly workstation 125 foruse with the prescription order processing system 100 (shown in FIG. 1).A coordinate system 127 includes an X-axis, a Y-axis, and a Z-axis. Inthis embodiment, the container disassembly workstation 125 is configuredto facilitate “bulking-up” of pharmaceuticals for filling orders in theprescription order processing system 100. More specifically, containerdisassembly workstation 125 includes a container manipulation device200, a cutter device 202, and a scanner device 204, each deviceconfigured to cooperate with each other device to facilitate removing aplurality of pharmaceuticals contained within a plurality of containersfor transferring to a bulk container 206. In the example embodiment, thebulk container is a one gallon container. The bulk containers 206 aretransported to a central location within the prescription orderprocessing system 100 to facilitate further distribution of thepharmaceuticals.

The container disassembly workstation 125 includes a holding area 208configured to retain a plurality of the containers 210 in a holdingposition 212 defined therein, a pharmaceutical receptacle 214 configuredto receive pharmaceuticals, a dust receptacle 215 configured to receivepharmaceutical dust, a container receptacle 216 configured to receive atleast a portion of the containers 210, a vacuum system 217, and acontainer receptacle bin 218. In this embodiment, the holding area 208includes a tray 220 including a plurality of holes defined therein, eachhole configured to receive one of the containers 210. In an additionalembodiment, the pharmaceutical receptacle 214 includes a door configuredto inhibit pharmaceuticals from entering the pharmaceutical receptacle214 until the door is in an open position. In some embodiments, theholding area 208 is configured to receive a crate, pallet or other typeof container retaining component that is pre-loaded with the containers210.

In this embodiment, the containers 210 are cylindrical hollow bottleshaving a body 222 and a lid 224. The body 222 includes a top 226 and abase 228, the top 226 being threaded to receive the lid 224 tofacilitate retaining a plurality of pharmaceuticals within the container210. A first portion 230 of the container 210 and a second portion 232of the container 210 are defined as illustrated in FIG. 4. In thisembodiment, the containers 210 are fabricated from a high-densitypolyethylene (HDPE) material. In some embodiments, the containers 210are fabricated from at least one of polyethylene terephthalate (PET), #2plastic, and #5 plastic. In additional embodiments, the containers 210may have any shape and configuration that facilitates operation ofprescription order processing system 100 as defined herein.

The scanner device 204 is coupled to container disassembly workstation125 and extends along the Z-direction above the holding area 208. Inthis embodiment, the scanner device 204 is a laser proximity sensor andis configured to determine if at least one container 210 is positionedin the holding position 212, wherein a container 210 is in the holdingposition 212 when the container 210 is oriented within the holding area208 such that the base 228 is positioned against the containerdisassembly workstation 125. In some embodiments, the scanner device 204may be one of an optical proximity sensor, an ultrasonic sensor, and acapacitive proximity sensor. Additionally, in this embodiment, thescanner device 204 is configured to determine a height, location, andorientation of the containers 210 in the holding area 208. In additionalembodiments, the scanner device 204 includes an array of scanner devices204 further configured to determine the type of the containers 210.

The container manipulation device 200 is configured to move at least oneof the containers 210 along at least one of the X-direction, theY-direction, and the Z-direction within a container disassemblyworkspace 234 defined by the container disassembly workstation 125. Morespecifically, the container manipulation device 200 is a collaborativerobot configured to move the container 210 between the holding position212, a cutter position 236, an emptying position 270, and a discardposition 272 to complete one cycle of the container disassemblyworkstation 125. In additional embodiments, the container manipulationdevice 200 is at least one of a selective-compliance-articulated robotarm, a six-axis robot, a cylindrical robot, a delta robot, a polarcoordinate robot, a vertically articulated robot, and a Cartesiancoordinate robot. In some embodiments, the container manipulation device200 is configured to move more than one container 210 during each cycleof the container disassembly workstation.

In this embodiment, the container manipulation device 200 is adapted tofacilitate the operator 107 working within the container disassemblyworkspace 234 without the container manipulation device 200 beingguarded from interaction with the operators 107. In some embodiments,the container disassembly workspace 234 is guarded from the operators107 by a guard configured to inhibit the operators 107 from interactingwith the container manipulation device 200 while the containermanipulation device 200 is operating. In some other embodiments, thecontainer disassembly workspace 234 is guarded from the operators 107 atleast partially by a sensor configured to detect entry of any portion ofan operator 107 into workspace 234 and to cause at least the containermanipulation device 200 to discontinue operation and movement.

FIG. 4 is a front view of the container 210 that may be used with thecontainer disassembly workstation 125 (shown in FIG. 3). FIG. 5 is aperspective view of the cutter device 202 for use with the containerdisassembly workstation 125 (shown in FIG. 3) illustrated in anon-cutting position 235. FIG. 6 is a plan view of the cutter device 202(shown in FIG. 5). The cutter device 202 is configured to separate atleast a first portion 230 of at least one of the containers 210 from asecond portion 232 of the container 210. In this embodiment, the cutterdevice 202 is an ultrasonic cutter configured to cut through walls of abottom portion 238 of the container 210 when the container 210 is in thecutter position 236 and includes a cutting force device 240 and a holderdevice 242 substantially surrounded by a plurality of guards 244. Theplurality of guards 244 facilitate reducing the operators 107 exposureto cutter device 202 and debris created during the cutting operation. Inthis embodiment, the plurality of guards 244 substantially surroundingthe cutter device 202 are oriented and positioned to facilitatedirecting at least one of the first portion 230 and the second portion232 of the container 210 to the container receptacle 216 following thecutting operation. In additional embodiments, the cutter device 202 maybe at least one of a rotary cutter, a rigid blade, and a thermal cutter.

In this embodiment, a working end 246 of the container manipulationdevice 200 includes a gripper device 248 configured to grip the firstportion 230 of the container 210 in a first, upright orientation 213 atthe holding position 212. More specifically, the gripper device 248 isconfigured to grip the container 210 such that a container longitudinalaxis 211 is substantially aligned with the Z-direction and the lid 224is vertically higher with respect to the Z-direction than the secondportion 232 when the container 210 is in the first orientation 213. Thegripper device 248 is a multiple-linkage two finger gripper device andis configured to grip containers 210 having a predetermined range ofouter diameters 252. In this embodiment, the gripper device 248 isconfigured to grip the container 210 around the lid 224, the lid havingan outer diameter 252 in a range of one half inch to five inches, andthe container 210 having a total container weight of less than 3 pounds.In some embodiments, the gripper device 248 may grip the container 210along any portion of the container 210 that facilitates operation of thecontainer disassembly workstation 125 as described herein. In additionalembodiments, gripper device 248 may be at least one of a three-fingergripper device, a multiple finger gripper device, or any other type ofgripper device configured to grip and retain at least one container 210.

The container manipulation device 200 is also configured to then movethe at least one container 210 from the holding position 212 in thefirst orientation 213 to the cutter position 236, proximate the cutterdevice 202. The container manipulation device 200 is further configuredto then orient the at least one container 210 in a second, upside-downorientation 254 at the cutter position 236. The holder device 242 isconfigured to engage the container 210 at the cutter position 236 and tostabilize the container 210 during operation of the cutter device 202.In this embodiment, the holder device 242 includes two arms 256 movablycoupled to the holder device 242 such that the arms 256 are able to movealong the X-direction in order to vary an arm gap 258 to facilitatereleasably retaining the containers 210 having outer diameters 252within a specified range. In this embodiment, at closing spring (notshown) biases the arms 256 towards each other. In additionalembodiments, the arms 256 may be biased towards each other using anycomponent that facilitates retention of the containers 210 by the holderdevice 242 during operation of the cutter device 202.

FIG. 7 is a perspective of the cutter device 202 (shown in FIG. 5)illustrated in the cutting position 237. FIG. 8 is a front view of thecutter device 202 (shown in FIG. 7). In this embodiment, the cutterdevice 202 is slideably coupled to a cutting force device 240. Thecutting force device is configured to bias the cutter device 202 along acutter axis 266 towards the cutting position 237 such that the cuttingforce device 240 generates a cutting force between the cutter device 202and the walls of the container 210 when the container 210 is in thecutter position 236. The cutting force device 240 is configured togenerate the cutting force until the cutter device 202 has cut throughthe walls of the container 210 and caused the first portion 230 to beseparated from the second portion 232 of the container 210.

In this embodiment, the cutter device 202 includes a cutter motor 260and a cutter head 262 mounted within a resonant mount 264 coupled to thecutting force device 240. The cutter head 262 is a carbide cutter head262. In some embodiments, the cutter head 262 may be fabricated from anymaterial that facilitates separation of the first portion 230 from thesecond portion 232. The cutter motor 260 is configured to cause thecutter head 262 to oscillate along the cutter axis 266 at a frequency ofthirty kilohertz (kHz). In additional embodiments, the cutter head 262may be caused to oscillate at a frequency in a range of twenty to fiftykHz. The high-frequency oscillations of the cutter head 262 facilitaterapid and precise separation of the first portion 230 from the secondportion 232 of the container 210, resulting in an opening to an innercavity of the container 210.

After the first portion 230 has been separated from the second portion232 of the container 210, a discard opening 268 receives the secondportion 232 and the container manipulation device 200 is configured tomove the first portion 230 from the cutter position 236 to an emptyingposition 270. In this embodiment, the emptying position 270 is definedabove the pharmaceutical receptacle 214 along the Z-direction. Thecontainer manipulation device 200 orients the container 210 in the firstorientation 213 and the plurality of pharmaceuticals are released fromthe inner cavity of the container 210 to the pharmaceutical receptacle214. In this embodiment, the container manipulation device 200 isconfigured to move to a plurality of positions along an XY plane withinan area defined by the emptying position 270 such that orienting thecontainer 210 in the first orientation 213 causes the pharmaceuticals tofall onto a different portion of the pharmaceutical receptacle 214 thanthe pharmaceuticals deposited on the pharmaceutical receptacle 214during the previous cycle of the container disassembly workstation 125.Additional packing materials such as cotton buffers and desiccants maybe stored within the internal cavity with the pharmaceuticals and theoperator 107 of the container disassembly workstation 125 may berequired to separate the packing materials from the pharmaceuticalswithin the pharmaceutical receptacle 214.

In this embodiment, after the pharmaceuticals have been emptied from thefirst portion 230, the container manipulation device 200 is configuredto move the first portion 230 from the emptying position 270 to adiscard position 272. In this embodiment, the discard position 272 isdefined above the discard opening 268 along the Z-direction. Thecontainer manipulation device 200 orients the first portion 230 abovethe discard opening 268 and releases the first portion 230 through thediscard opening 268 to the container receptacle 216. In someembodiments, the container manipulation device 200 is configured to movethe pharmaceuticals that have been emptied onto the pharmaceuticalreceptacle 214 from the pharmaceutical receptacle 214 to a bulkcontainer 206. The above-described cycle continues until none of thecontainers 210 are present in the holding area 208, or until thecontainer disassembly workstation 125 is otherwise caused to stop.

FIG. 9 is an example process flow illustrating a method 300 fordisassembling a container 210 that contains pharmaceuticals. Method 300includes scanning 302 a holding area 208 to determine if at least onecontainer 210 containing a plurality of pharmaceutical products ispositioned in a holding position 212 of the holding area 208 of acontainer disassembly workstation 125. Method 300 also includescapturing 304 the at least one container 210 with a containermanipulation device 200. Method 300 further includes moving 306 the atleast one container 210 from the holding position 212 to a cutterposition 236 proximate a cutter device 202. Method 300 includesseparating 308 a first portion 230 of the at least one container 210from a second portion 232 of the at least one container 210 using thecutter device 202. Method 300 includes transferring 310 the plurality ofpharmaceutical products from at least one of the first portion 230 andthe second portion 232 to a pharmaceutical receptacle 214, wherein thepharmaceutical receptacle 214 is configured to receive the plurality ofpharmaceutical products. Finally, method 300 includes placing 312 atleast one of the first portion 230 and the second portion 232 in acontainer receptacle 216, wherein the container receptacle 216 isconfigured to receive at least one of the first portion 230 of the atleast one container 210 and the second portion 232 of the at least onecontainer 210.

Embodiments of the methods and systems described herein achieve superiorresults as compared to prior methods and systems. For example, unlikeknown pharmaceutical unpacking and combining systems, the pharmaceuticalcontainer disassembly and pharmaceutical bulk packaging systemsdescribed herein are configured to operate with minimal operator inputand interaction with the workstation. In particular, the containerdisassembly workstations described are operable such that a plurality ofpharmaceutical containers may be disassembled, and the pharmaceuticalscontained therein removed, with reduced operator input required ascompared to known systems, enabling an operator to operate multiplecontainer disassembly workstations simultaneously. As a result,specialty and custom pharmacies can be retrofitted with the containerdisassembly workstations, thereby increasing the safety and efficiencyof existing specialty and custom pharmacies. These workstations can havecontainer manipulation devices that do not require guarding incorporatedinto the workstation such that the operator is able to work in the sameworkspace as the container manipulation device, further improving safetyand efficiency of the workstation. Further, unlike some knownpharmaceutical unpacking and combining systems that depend on theoperator to feed containers into the unpacking and combining system, theworkstations described herein allow an operator to place containers in adesignated holding area where a scanner scans the containers andprovides their locations and container types to the containermanipulation device for processing, further improving the efficiency ofthe system. Additionally, unlike some known pharmaceutical unpacking andcombining systems, the workstations described herein do not require theoperators to manually remove, cut, or open any portion of the containerto release the pharmaceuticals, improving operator safety and systemefficiency.

The term “based on” or using, as used herein, reflects an open-endedterm that can reflect others elements beyond those explicitly recited.Certain systems, apparatus, applications or processes are describedherein as including a number of modules. A module may be a unit ofdistinct functionality that may be presented in software, hardware, orcombinations thereof. When the functionality of a module is performed inany part through software, the module includes a computer-readablemedium. The modules may be regarded as being communicatively coupled.

The embodiments of the present disclosure generally provide for aplurality of circuits or other electrical devices, which can be used inunits, modules, systems, and sub-systems and the like. All references tosuch and the functionality provided by each are not intended to belimited to encompassing only what is illustrated and described herein.While particular labels may be assigned to the various circuits or otherelectrical devices disclosed, such labels are not intended to limit thescope of operation for the circuits and the other electrical devices.Such circuits and other electrical devices may be combined with eachother and/or separated in any manner based on the particular type ofelectrical/operational implementation that is desired. It is recognizedthat any circuit or other electrical device disclosed herein may includeany number of microprocessors, discrete circuit components, integratedcircuits, memory devices (e.g., FLASH, random access memory (RAM), readonly memory (ROM), electrically programmable read only memory (EPROM),electrically erasable programmable read only memory (EEPROM), or othersuitable variants thereof, etc.) and instructions (e.g., software, etc.)which co-act with one another to perform operation(s) disclosed herein.In addition, any one or more than one electric devices may be configuredto execute a computer-program that is embodied in a computer readablemedium that is programmed to perform any number of the functions andfeatures as disclosed. The computer readable medium may benon-transitory or in any form readable by a machine or electricalcomponent.

At least some portions of the present disclosure may be accomplished byusing a robot. A robot can be a machine capable of carrying out acomplex series of actions automatically. These complex series of actionsmay include picking up, orientating, positioning and/or releasing aprescription component, a pill, a container or other structure. Therobot may be dedicated to a single series of movements or may be able toexecute multiple series of movements. A robot may include a processorthat received instructions and then executes instructions to control itsmovement. In another example, a robot may resemble a human being andreplicate certain human movements and functions, may move location, havean articulated arm, have grasping structures that replicate fingers anddo not damage containers, and the like.

Methods and systems for pharmacy order processing have been described.Although embodiments of the present disclosure have been described withreference to specific example embodiments, it will be evident thatvarious modifications and changes may be made to these embodimentswithout departing from the broader spirit and scope of the embodimentsof the disclosure. Accordingly, the specification and drawings are to beregarded in an illustrative rather than a restrictive sense.

The methods described herein do not have to be executed in the orderdescribed, or in any particular order. Moreover, various activitiesdescribed with respect to the methods identified herein can be executedin serial or parallel fashion. Although “End” blocks may be shown in theflowcharts, the methods may be performed continuously.

In the foregoing, it can be seen that various features are groupedtogether in a single embodiment for the purpose of streamlining thedisclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter may lie in less thanall features of a single disclosed embodiment. Thus, the followingclaims are hereby incorporated into the Detailed Description, with eachclaim standing on its own as a separate embodiment.

The foregoing description is merely illustrative in nature and is in noway intended to limit the disclosure, its application, or uses. Thebroad teachings of the disclosure can be implemented in a variety offorms. Therefore, while this disclosure includes particular examples,the true scope of the disclosure should not be so limited since othermodifications will become apparent upon a study of the drawings, thespecification, and the following claims. It should be understood thatone or more than one steps within a method may be executed in differentorder (or concurrently) without altering the principles of the presentdisclosure. Further, although each of the embodiments is described aboveas having certain features, any one or more than one of those featuresdescribed with respect to any embodiment of the disclosure can beimplemented in and/or combined with features of any of the otherembodiments, even if that combination is not explicitly described. Inother words, the described embodiments are not mutually exclusive, andpermutations of one or more than one embodiments with one another remainwithin the scope of this disclosure.

Spatial and functional relationships between elements (for example,between modules, circuit elements, semiconductor layers, etc.) aredescribed using various terms, including “connected,” “engaged,”“coupled,” “adjacent,” “next to,” “on top of” “above,” “below,” and“disposed.” Unless explicitly described as being “direct,” when arelationship between first and second elements is described in the abovedisclosure, that relationship can be a direct relationship where noother intervening elements are present between the first and secondelements, but can also be an indirect relationship where one or morethan one intervening elements are present (either spatially orfunctionally) between the first and second elements. As used herein, thephrase at least one of A, B, and C should be construed to mean a logical(A OR B OR C), using a non-exclusive logical OR, and should not beconstrued to mean “at least one of A, at least one of B, and at leastone of C.”

In this application, including the definitions below, the term ‘module’or the term ‘controller’ may be replaced with the term ‘circuit.’ Theterm ‘module’ may refer to, be part of, or include: an ApplicationSpecific Integrated Circuit (ASIC); a digital, analog, or mixedanalog/digital discrete circuit; a digital, analog, or mixedanalog/digital integrated circuit; a combinational logic circuit; afield programmable gate array (FPGA); a processor circuit (shared,dedicated, or group) that executes code; a memory circuit (shared,dedicated, or group) that stores code executed by the processor circuit;other suitable hardware components that provide the describedfunctionality; or a combination of some or all of the above, such as ina system-on-chip.

The module may include one or more than one interface circuits. In someexamples, the interface circuits may include wired or wirelessinterfaces that are connected to a local area network (LAN), theInternet, a wide area network (WAN), or combinations thereof. Thefunctionality of any given module of the present disclosure may bedistributed among multiple modules that are connected via interfacecircuits. For example, multiple modules may allow load balancing. In afurther example, a server (also known as remote, or cloud) module mayaccomplish some functionality on behalf of a client module.

The term code, as used above, may include software, firmware, and/ormicrocode, and may refer to programs, routines, functions, classes, datastructures, and/or objects. The term shared processor circuitencompasses a single processor circuit that executes some or all codefrom multiple modules. The term group processor circuit encompasses aprocessor circuitry that, in combination with additional processorcircuits, executes some or all code from one or more than one modules.References to multiple processor circuits encompass multiple processorcircuits on discrete dies, multiple processor circuits on a single die,multiple cores of a single processor circuit, multiple threads of asingle processor circuit, or a combination of the above. The term sharedmemory circuit encompasses a single memory circuit that stores some orall code from multiple modules. The term group memory circuitencompasses a memory circuit that, in combination with additionalmemories, stores some or all code from one or more than one modules.

The term memory circuit is a subset of the term computer-readablemedium. The term computer-readable medium, as used herein, does notencompass transitory electrical or electromagnetic signals propagatingthrough a medium (such as on a carrier wave); the term computer-readablemedium may therefore be considered tangible and non-transitory.Non-limiting examples of a non-transitory, tangible computer-readablemedium are nonvolatile memory circuits (such as a flash memory circuit,an erasable programmable read-only memory circuit, or a mask read-onlymemory circuit), volatile memory circuits (such as a static randomaccess memory circuit or a dynamic random access memory circuit),magnetic storage media (such as an analog or digital magnetic tape or ahard disk drive), and optical storage media (such as a CD, a DVD, or aBlu-ray Disc).

The systems and methods described in this application may be partiallyor fully implemented by a special purpose computer created byconfiguring a general purpose computer to execute one or more than oneparticular functions embodied in computer programs. The functionalblocks and flowchart elements described above serve as softwarespecifications, which can be translated into the computer programs bythe routine work of a skilled technician or programmer.

The computer programs include processor-executable instructions that arestored on at least one non-transitory, tangible computer-readablemedium. The computer programs may also include or rely on stored data.The computer programs may encompass a basic input/output system (BIOS)that interacts with hardware of the special purpose computer, devicedrivers that interact with particular devices of the special purposecomputer, one or more than one operating systems, user applications,background services, background applications, etc.

The computer programs may include: (i) descriptive text to be parsed,such as HTML (hypertext markup language) or XML (extensible markuplanguage), (ii) assembly code, (iii) object code generated from sourcecode by a compiler, (iv) source code for execution by an interpreter,(v) source code for compilation and execution by a just-in-timecompiler, etc. As examples only, source code may be written using syntaxfrom languages including C, C++, C#, Objective-C, Swift, Haskell, Go,SQL, R, Lisp, Java®, Fortran, Perl, Pascal, Curl, OCaml, Javascript®,HTML5 (Hypertext Markup Language 5th revision), Ada, ASP (Active ServerPages), PHP (PHP: Hypertext Preprocessor), Scala, Eiffel, Smalltalk,Erlang, Ruby, Flash®, Visual Basic®, Lua, MATLAB, SIMULINK, and Python®.

None of the elements recited in the claims are intended to be ameans-plus-function element within the meaning of 35 U.S.C. § 112(f)unless an element is expressly recited using the phrase “means for,” orin the case of a method claim using the phrases “operation for” or “stepfor.”

Embodiments for pharmacy order processing are described above in detail.The systems and methods of operating such systems are not limited to thespecific embodiments described herein, but rather, components of systemsand/or steps of the methods may be utilized independently and separatelyfrom other components and/or steps described herein. For example, themethods may also be used in combination with other systems andenvironments and are not limited to the environments as describedherein. Rather, the embodiments can be implemented and utilized inconnection with many other applications.

In this specification and the claims, reference is made to a number ofterms, which shall be defined to have the following meanings:

The singular forms “a”, “an”, and “the” include plural references unlessthe context clearly dictates otherwise.

“Optional” or “optionally” means that the subsequently described eventor circumstance may or may not occur, and that the description includesinstances where the event occurs and instances where it does not.

The term “non-transitory computer-readable media” is intended to berepresentative of any tangible computer-based device implemented in anymethod or technology for short-term and long-term storage ofinformation, such as, computer-readable instructions, data structures,program modules and sub-modules, or other data in any device. Therefore,the methods described herein may be encoded as executable instructionsembodied in a tangible, non-transitory, computer readable medium,including, without limitation, a storage device and/or a memory device.Such instructions, when executed by a processor, cause the processor toperform at least a portion of the methods described herein. Moreover, asused herein, the term “non-transitory computer-readable media” includesall tangible, computer-readable media, including, without limitation,non-transitory computer storage devices, including, without limitation,volatile and nonvolatile media, and removable and non-removable mediasuch as a firmware, physical and virtual storage, cd-roms, dvds, and anyother digital source such as a network or the internet, as well as yetto be developed digital means, with the sole exception being atransitory, propagating signal.

The terms “software” and “firmware” are interchangeable, and include anycomputer program stored in memory for execution by devices that include,without limitation, mobile devices, clusters, personal computers,workstations, clients, and servers.

The term “computer” and related terms, e.g., “computing device”, are notlimited to integrated circuits referred to in the art as a computer, butbroadly refers to a microcontroller, a microcomputer, a programmablelogic controller (plc), an application specific integrated circuit, andother programmable circuits, and these terms are used interchangeablyherein.

Computer systems are described, and such computer systems include aprocessor and a memory. However, any processor in a computer devicereferred to may also refer to one or more processors wherein theprocessor may be in one computing device or a plurality of computingdevices acting in parallel, such as in a cloud computing environment.Additionally, any memory in a computer device referred to may also referto one or more memories, wherein the memories may be in one computingdevice or a plurality of computing devices acting in parallel.

A processor may include any programmable system including systems usingmicro-controllers, reduced instruction set circuits (rise), applicationspecific integrated circuits (asics), logic circuits, and any othercircuit or processor capable of executing the functions describedherein. The above examples are example only, and are thus not intendedto limit in any way the definition and/or meaning of the term“processor.” The term “database” may refer to either a body of data, arelational database management system (rdbms), or to both. A databasemay include any collection of data including hierarchical databases,relational databases, flat file databases, object-relational databases,object oriented databases, and any other structured collection ofrecords or data that is stored in a computer system. The above are onlyexamples, and thus are not intended to limit in any way the definitionand/or meaning of the term database. Examples of rdbms's include, butare not limited to including, Oracle® Database, Mysql, IBM® Db2,Microsoft® Sql Server, Sybase®, and Postgresql. However, any databasemay be used that enables the systems and methods described herein.(oracle is a registered trademark of Oracle Corporation, Redwood Shores,Calif.; IBM is a registered trademark of International Business MachinesCorporation, Armonk, new York; Microsoft is a registered trademark ofMicrosoft Corporation, Redmond, Wash.; and Sybase is a registeredtrademark of Sybase, Dublin, Calif.)

In some embodiments, a computer program is embodied on a computerreadable medium. In other embodiments, the system is executed on asingle computer system, without requiring a connection to a servercomputer. In still other embodiments, the system is run in a Windows®environment (windows is a registered trademark of microsoft corporation,Redmond, Wash.). In yet another embodiment, the system is run on amainframe environment and a Unix® server environment (Unix is aregistered trademark of x/open company limited located in reading,Berkshire, United Kingdom). The application is flexible and designed torun in various different environments without compromising any majorfunctionality. In some embodiments, the system includes multiplecomponents distributed among a plurality of computing devices. One ormore components may be in the form of computer-executable instructionsembodied in a computer-readable medium.

Approximating language, as used herein throughout the specification andclaims, may be applied to modify any quantitative representation thatcould permissibly vary without resulting in a change in the basicfunction to which it is related. Accordingly, a value modified by a termor terms, such as “about” and “substantially”, are not to be limited tothe precise value specified. In at least some instances, theapproximating language may correspond to the precision of an instrumentfor measuring the value. Here and throughout the specification andclaims, range limitations may be combined and/or interchanged; suchranges are identified and include all the sub-ranges contained thereinunless context or language indicates otherwise.

The inventive subject matter may be represented in a variety ofdifferent embodiments of which there are many possible permutations.Although specific features of various embodiments of the invention maybe shown in some drawings and not in others, this is for convenienceonly. In accordance with the principles of the invention, any feature ofa drawing may be referenced and/or claimed in combination with anyfeature of any other drawing. This written description uses examples todisclose the invention, including the best mode, and also to enable anyperson skilled in the art to practice the invention, including makingand using any devices or systems and performing any incorporatedmethods. The patentable scope of the invention is defined by the claims,and may include other examples that occur to those skilled in the art.Such other examples are intended to be within the scope of the claims ifthey have structural elements that do not differ from the literallanguage of the claims, or if they include equivalent structuralelements with insubstantial differences from the literal language of theclaims.

We claim:
 1. A pharmacy container processing system comprising: a cutterincluding a cutter head adapted to cut through at least one wall of acontainer to separate first portion of the container from a secondportion of the container with at least one container being in a cutterposition; a container manipulation device including a gripper to holdthe container, the container manipulation device being configured tomove the container between a holding position and the cutter position,the container manipulation device being further configured to move thefirst portion of the at least one container from the cutter position toan emptying position whereat contents are removed from the first portionof the container; a content receptacle being position to receive thecontents from the first portion of the container at the emptyingposition; and a container receptacle defining an opening sized toreceive the first portion of the at least one container and the secondportion of the at least one container with the gripper releasing thecontainer.
 2. The system of claim 1, wherein the content receptacleincludes a bulk container area including a bulk container that isconfigured to receive a plurality of pharmaceuticals from the containerreceptacle.
 3. The system of claim 1, wherein the content receptaclereceives the contents after the first portion of the container is cutfrom the second portion of the container and the first portion, whichcontains the contents, is moved to the emptying position by thecontainer manipulation device.
 4. The system of claim 1, wherein thegripper is at least one of a multiple finger gripper device and amultiple-linkage gripper device, and wherein the gripper is configuredto grip the at least one container having an outer diameter within apredetermined range of outer diameters, and wherein the gripper invertsthe container when at the emptying position.
 5. The system of claim 1,wherein the container manipulation device is further configured to: gripthe first portion of the container in a first, upright orientation atthe holding position; move the container from the holding position tothe cutter position; orient the container in a second, invertedorientation at the cutter position; and orient the first portion of thecontainer in the first orientation at the emptying position.
 6. Thesystem of claim 1, further including a scanner device configured todetermine when the container is positioned in the holding position. 7.The system of claim 1, wherein the container manipulation deviceincludes a holder device configured to stabilize the at least onecontainer during operation of the cutter.
 8. The system of claim 1,wherein the cutter is one of an ultrasonic cutter, a rotary cutter, anda thermal cutter, or a combination thereof.
 9. The system of claim 1,wherein the cutter includes a cutting force device, wherein the cuttingforce device is configured to generate a cutting force between thecutter and the at least one container in the cutter position.
 10. Apharmacy container processing system comprising: a cutter including acutter head adapted to cut through a wall of a container to create anopening in the wall into a container interior whereat pharmaceuticalcontents are stored with the container being in a cutter position; acontainer manipulation device including a gripper to hold the containerwhen engaged by the cutter head, the container manipulation device beingconfigured to move the container between a holding position, the cutterposition, and an emptying position, the container manipulation devicebeing further configured to invert the container between at least one ofthe holding position and the cutter position or the cutter position andthe emptying position, the container manipulation device beingconfigured to move the container between the cutter position and theemptying position whereat contents are removed from the first portion ofthe container; a content receptacle being position to receive thepharmaceutical contents from the container interior of the containerwith the container at the emptying position; and a container receptacledefining an opening sized to receive the container after thepharmaceutical contents are removed from the container held at theemptying position and after the gripper releasing the container.
 11. Thesystem of claim 10, wherein the content receptacle includes a bulkcontainer area including a bulk container that is configured to receivea plurality of pharmaceuticals from the container receptacle.
 12. Thesystem of claim 10, wherein the content receptacle receives the contentsafter the first portion of the container is cut from the second portionof the container and the first portion, which contains the contents, ismoved to the emptying position by the container manipulation device. 13.The system of claim 10, wherein the cutter includes a cutting forcedevice, wherein the cutting force device is configured to generate acutting force between the cutter and the at least one container in thecutter position.
 14. The system of claim 10, wherein the containermanipulation device includes a scanning device configured to determinewhen the container is positioned in the holding position.
 15. The systemof claim 10, wherein the container manipulation device includes a holderdevice configured to stabilize the at least one container duringoperation of the cutter.
 16. A container disassembly workstationdefining a container disassembly workspace, the container disassemblyworkstation comprising: a holding area sized to retain a plurality ofcontainers in a holding position, wherein a plurality of pharmaceuticalcontents are contained within the plurality of containers; a cutterdevice comprising a cutter head and configured to cut through at leastone wall of at least one container to create a first portion of thecontainer of the plurality of containers from a second portion of thecontainer when the container is in a cutter position to open the wall toprovide access to an interior of the container; a robotic arm comprisinga gripper, the robotic arm configured to move the container from theholding position to the cutter position and to an emptying positionwithin the container disassembly workspace, the robotic arm configuredto rotate about at least a first axis and a second axis, the first axisand the second axis being non-parallel with one another; and apharmaceutical content receptacle sized to receive the plurality ofpharmaceutical contents with access through the wall to the interior ofthe container at the emptying position, wherein the plurality ofpharmaceutical contents are received from the container after the firstportion of the at least one container is opened from the second portionof the container.
 17. The workstation of claim 16, wherein the roboticarm is further configured to: grip the first portion of the at least onecontainer in a first, upright orientation at the holding position; movethe container from the holding position to the cutter position; orientthe container in a second, upside-down orientation at the cutterposition; move the first portion of the at least one container from thecutter position to an emptying position where the pharmaceuticalcontents are removed from the first portion of the container; and orientthe first portion of the container in the first orientation at theemptying position.
 18. The workstation of claim 16, wherein thecontainer disassembly workstation includes a holder device configured tostabilize the container during operation of the cutter device.
 19. Theworkstation of claim 16, wherein the container disassembly workstationincludes a container receptacle defining an opening sized to receive thefirst portion of the container, the second portion of the container, orboth.
 20. The workstation of claim 19, wherein the cutter deviceincludes a cutting force device, wherein the cutting force device isconfigured to generate a cutting force between the cutter device and theat least one container in the cutter position; and wherein thepharmaceutical receptacle and the container receptacle are fixedrelative to one another in the container disassembly workspace.